Reverse proxy for cloud security

ABSTRACT

The technology disclosed relates to accessing a hosted service on a client device. In particular, the technology disclosed relates to receiving, on a client device of an entity&#39;s user, from a network security system, a forwarding rule for modifying requests for accessing a hosted service, receiving on the client device a request for accessing the hosted service, using the forwarding rule to modify the request for accessing the hosted service and generating a modified request for accessing the hosted service, and receiving on the client device a response from the network security system.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No. 16/554,482, entitled “POINTS OF PRESENCE (POPS) ARCHITECTURE FOR CLOUD SECURITY,” filed on 28 Aug. 2019 (Attorney Docket No. NSKO 1000-14), which is a continuation of U.S. application Ser. No. 15/990,507, entitled “DEEP APPLICATION PROGRAMMING INTERFACE INSPECTION (DAPII) FOR CLOUD SECURITY,” filed on 25 May 2018 (Attorney Docket No. NSKO 1000-7), which is a continuation of U.S. application Ser. No. 15/213,250, entitled “LOGGING AND MONITORING USAGE OF CLOUD-BASED HOSTED STORAGE SERVICES,” filed on 18 Jul. 2016 (Attorney Docket No. NSKO 1000-6), which is a continuation of U.S. application Ser. No. 14/198,499, entitled “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on 5 Mar. 2014 (Attorney Docket No. NSKO 1000-2), which claims the benefit of U.S. provisional Patent Application No. 61/773,633, entitled, “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on Mar. 6, 2013 (Attorney Docket No. NSKO 1000-1);

This application is a continuation of U.S. application Ser. No. 16/554,482, entitled “POINTS OF PRESENCE (POPS) ARCHITECTURE FOR CLOUD SECURITY,” filed on 28 Aug. 2019 ((Attorney Docket No. NSKO 1000-14), which is a continuation of U.S. application Ser. No. 15/990,509, entitled “CONTEXT-AWARE DATA LOSS PREVENTION (DLP) FOR CLOUD SECURITY,” filed on 25 May 2018 (Attorney Docket No. NSKO 1000-8), which is a continuation of U.S. application Ser. No. 15/213,250, entitled “LOGGING AND MONITORING USAGE OF CLOUD-BASED HOSTED STORAGE SERVICES,” filed on 18 Jul. 2016 (Attorney Docket No. NSKO 1000-6), which is a continuation of U.S. application Ser. No. 14/198,499, entitled “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on 5 Mar. 2014 (Attorney Docket No. NSKO 1000-2), which claims the benefit of U.S. provisional Patent Application No. 61/773,633, entitled, “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on Mar. 6, 2013 (Attorney Docket No. NSKO 1000-1); and

This application is a continuation of U.S. application Ser. No. 16/554,482, entitled “POINTS OF PRESENCE (POPS) ARCHITECTURE FOR CLOUD SECURITY,” filed on 28 Aug. 2019 ((Attorney Docket No. NSKO 1000-14), which is a continuation of U.S. application Ser. No. 15/990,512, entitled “APPLICATION PROGRAMMING INTERFACE (API)-BASED SECURITY FOR WEBSITES,” filed on 25 May 2018 (Attorney Docket No. NSKO 1000-9), which is a continuation of U.S. application Ser. No. 15/213,250, entitled “LOGGING AND MONITORING USAGE OF CLOUD-BASED HOSTED STORAGE SERVICES,” filed on 18 Jul. 2016 (Attorney Docket No. NSKO 1000-6), which is a continuation of U.S. application Ser. No. 14/198,499, entitled “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on 5 Mar. 2014 (Attorney Docket No. NSKO 1000-2), which claims the benefit of U.S. provisional Patent Application No. 61/773,633, entitled, “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on Mar. 6, 2013 (Attorney Docket No. NSKO 1000-1).

The priority provisional and non-provisional applications are hereby incorporated by reference for all purposes.

This application is related to U.S. patent application Ser. No. 14/198,508, entitled “SECURITY FOR NETWORK DELIVERED SERVICES,” filed on 5 Mar. 2014 (Attorney Docket No. NSKO 1000-3). The related application is incorporated by reference for all purposes.

FIELD OF THE TECHNOLOGY DISCLOSED

This disclosure is generally related to providing visibility, control and data security for network delivered services.

BACKGROUND

The use of hosted services for a number of corporate functions is now common. Thus, instead of installing servers within a corporate network to run a customer relationship management (CRM) software product, a software as a service (SaaS) solution such as Salesforce.com's offerings can be used. The IT and network architecture approaches that could log and protect access to a classic solution provide limited control. The sprawl of BYOD and the need haul that traffic back to the enterprise make it less attractive. For example, VPN solutions are used to control access to the protected corporate network. Proxies (both transparent and explicit) may be used to filter, or limit access to undesirable web sites when the client is accessing the web sites from within the corporate network. Similar filtering software can be installed on client computers, e.g. safe browsing software, to enforce limits on access. A viable solution should provide consistent, centrally administered control, e.g. enforce the same policy across multiple devices, network services, and networks—including corporate networks.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows an architectural level schematic of a system in accordance with an embodiment.

FIG. 2 shows the virtual network topology of a system in accordance with an embodiment.

FIG. 3 shows a more detailed network topology and data flow of a system in accordance with an embodiment.

FIGS. 4-5 are process flow diagrams for policy enforcement.

FIG. 6 shows an architectural level schematic of a data plane point of presence.

FIG. 7 shows an architectural level schematic of a management plane point of presence.

FIGS. 8-9 are exemplary application definitions.

FIG. 10 is a process flow diagram for a more detailed policy filtering process.

FIG. 11 is an exemplary event log entry.

DETAILED DESCRIPTION Overview

The discussion is organized as follows. First, an introduction describing some of the problems addressed by various embodiments will be presented, followed by an explanation of terminology that will be used throughout the discussion. Then, a high-level description of one embodiment will be discussed at an architectural level. Next, the algorithms used by some embodiments to provide security are discussed. Lastly, more detailed architectures for implementing the system, together with filtering rules, models, and application definitions, are discussed.

We describe a system and various embodiments for providing security for network delivered services. Consider the problems faced primarily by corporations seeking to protect their data at the intersection of a bring your own device (BYOD) environment and the proliferation of hosted services. The company may be using Salesforce.com for CRM, Dropbox for storage, and Google Apps for collaboration. While users' devices are using the corporate network, the corporation may have some ability to log and monitor usage of these hosted services with existing network monitoring tools. However, if a user uses the Salesforce.com application with their mobile device over the cellular network, the user's activity is not trackable. Additionally, the trend towards BYOD may also increase the likelihood of enterprise traffic bypassing corporate networks completely.

Further, the activity that is tracked with traditional approaches is very much at the network level. What if you want to log data exports activity from the application? Track large downloads? Only allow users to access certain data or services while their location is within the European Union? Additionally, the system is compatible with existing VPNs, proxies, firewalls, and filtering systems. Thus, one policy could require that access to a particular hosted service by a particular user must be from client devices that are logged into the corporate VPN. For business applications developed by combining components from multiple web application services (sometimes called “mash-ups”), one embodiment provides a consistent, enterprise-wide application level control and policy enforcement.

Some individual hosted services may offer differing levels of security and access controls; one is limited to the specific items implemented by the hosted services as opposed to a uniform, programmable set of controls across multiple hosted applications. This enables the system to provide access controls and event logging that exceed the native capabilities of the hosted service.

One workaround companies use is to require hosted service vendors to deploy into private clouds within the corporate network. Aside from the previously discussed limitations, private clouds require that the company backhaul data to your corporate network for monitoring. In contrast, embodiments provide for centralized client corporate analytics across hosted services. Secondly, some embodiments provide for intentionally allowing “one more” access by a computer that is believed compromised. This approach may allow for better recovery of lost or stolen client devices because the access can be logged. Other embodiments assist in identifying hosted services that should be deactivated for individual users, e.g. user attempts to access service are reported even if the user should no longer have access. Embodiments can also interoperate with single sign-on (SSO) solutions and/or corporate identity directories, e.g. Microsoft's Active Directory. Such embodiments may allow policies to be defined in the directory, e.g. either at the group or user level, using custom attributes.

Also, it should be mentioned that another feature of embodiments is that hosted services configured with the system are also configured to require traffic via the system. This can be done through setting IP range restrictions in the hosted service to the IP range of the system and/or integration between the system and SSO systems. For example, integration with a SSO solution can enforce client presence requirements before authorizing the sign-on. Other embodiments may use “proxy accounts” with the SaaS vendor—e.g. a dedicated account held by the system that holds the only credentials to sign in to the service. In other embodiments, the client may encrypt the sign on credentials before passing the login to the hosted service; this means that the networking security system “owns” the password.

Terminology

Throughout this specification the following terms will be used:

Hosted Service: A hosted service refers to a network hosted service or application, accessed via a uniform resource locator (URL). Examples include both software as a service (SaaS) offerings, platform as a service (PaaS) offerings, infrastructure as a service (IaaS) offerings, as well as internal enterprise applications that are exposed via URLs. Examples of common hosted services today include Salesforce.com, Box.net, Dropbox, Google Apps, Amazon AWS, Microsoft Office 365, Workday, Oracle on Demand, Taleo, Yammer, and Concur. Hosted services provide functionality to users that is implemented in the cloud and that is the target of policies, e.g. logging in, editing documents, downloading bulk data, reading customer contact information, entering payables, deleting documents, in contrast to the offerings of a simple website and ecommerce sites. Note that some consumer facing websites, e.g. Facebook, can be quite complex; however, they lack the concept of a managed/corporate grouping of users and/or data that could be subject to custom policies. Thus Yammer which offers a social network for corporations is the type of hosted service considered here, while the current consumer-oriented Facebook is not. Some services, e.g. Google's Gmail can be a hybrid with some free users using the application generally while other corporations use it as a hosted service. Note that embodiments can support both web browser clients and application clients that use URL-based APIs. Thus, using Dropbox as an example, user activity on the Dropbox website, as well as activity of the Dropbox client on the computer could be monitored.

User Identity: User identity, or user identification, in the context of this specification refers to an indicator that is provided by the network security system to the client device. It may be in the form of a token, a unique identifier such as a UUID, a public-key certificate, or the like. In some embodiments, the user identity may be linked to a specific user and a specific device; thus, the same individual may have a different user identity on their mobile phone vs. their computer. The user identity may be linked to an entry or userid corporate identity directory, but is distinct from it. In one embodiment, a cryptographic certificate signed by the network security is used as the user identity. In other embodiments, the user identity may be solely unique to the user and be identical across devices.

Policy: The term policy, sometimes also referred to as a policy definition or policy data, refers to a machine-readable representation of flow control and logging requirements for hosted services. Typically, a policy is defined by one or more administrators at a corporation, or other entity, and is enforced upon users within that corporation, or entity. It is possible for individuals to define policies for their own usage that are enforced upon them; however, corporate usage is the more common case. It is also possible for a policy to be enforced on visitors or customers of a hosted service, e.g. where a corporation hosts a service and requires visiting customers to adhere to the policy for use. Of particular note is that the policies considered herein are capable of being sensitive to the semantics of a hosted application, which is to say a policy can differentiate between logging in to a hosted service from, say, editing documents on the hosted service. Context is important for understanding usage; for an entity, the collection of dozens or hundreds of individual policies (e.g. log bulk downloads, prohibit editing documents on the service, only allow bulk downloads for users who are in the “Vice President” group) is referred to singularly as one policy, or one policy definition. Thus, a system supporting multiple entities will generally have one policy per entity, each made up of dozens or hundreds of individual flow control and logging policies. Similarly, as discussed infra, the policy that is transferred to individual computers may be a subset of a full corporate policy, e.g. solely a machine-readable representation of the URLs of interest, as opposed to the full policy specification for each URL describing the flow control and/or logging behaviors.

Mobile and Tablet vs. Computer: Portions of the specification may make distinctions between two types of client devices used by users to access hosted services. The primary distinction is between the mechanisms for coupling the client device to the network security system. In relation to client devices, the term “computer” will refer to more open systems where the network security system can more directly install software and modify the networking stack. Similarly, in relation to client devices, the terms “mobile” or “tablet” will refer to more closed systems where the network security system options for modifying the network stack are more limited. This terminology mirrors the situation today where computer-client devices running Mac OS X, Windows desktop versions, and/or Linux can be more easily modified than mobile or tablet devices running iOS, Android, and/or Windows Mobile. Thus, the terminology refers to how third-party operating system vendor limitations are addressed to provide access to the network security system as opposed to a fundamental technical difference between the types of client devices. Further, if mobile OS vendors open their systems further, it is likely that the distinction could be eliminated with more classes of client devices using the embodiment described in the computer-client discussions. Additionally, it may be the case that certain server computers and other computing devices within an organization may have the client installed to cover machine-to-machine communications.

A closely related point is that some clients interface with the network security system differently. The browser add-on clients, for example, redirect the browsers to an explicit proxy. Only the traffic needed to apply the policy to is rerouted and it is done so within the application. The traffic arriving at the network security system can have the user identity embedded in the data or within the secure tunnel headers, e.g. additional headers or SSL client side certificates in some embodiments. Other clients redirect select network traffic through transparent proxies. For these connections, some traffic beyond exactly those requests needed by the policy may be routed to the network security system. Further, the user identity information is generally not within the data itself, but rather established by the client in setting up a secure tunnel to the network security system.

System Overview

We describe a system and various embodiments for providing security for network delivered services. The system and processes will be described with reference to FIG. 1 showing an architectural level schematic of a system in accordance with an embodiment. Because FIG. 1 is an architectural diagram, certain details are intentionally omitted to improve the clarity of the description. The discussion of FIG. 1 will be organized as follows. First, the elements of the figure will be described, followed by their interconnections. Then, the use of the elements in the system will be described in greater detail.

FIG. 1 includes the system 100. The system 100 includes network security system 120, management clients 130, the hosted services 140, client devices 150, and network 160. The network security system 120 includes the controller 121 and storage 122. The storage 122 stores, among other things, policies 181, clients 182, and user identities 183. See the discussion of FIGS. 6-7 for additional items that are typically included in the storage 122. The network security system 120 can be viewed as providing several functionalities 125; key among them are a management plane 126 and a data plane 127. The management clients 130 include tablet 132 and mobile 134. The hosted services 140 include the hosted service 142 and the hosted service 144. The client devices 150 include the mobile 152 and the computer 154. The mobile 152 includes an AppWrapper 157 and a VPN on demand 158. The computer 154 includes a client 155 which in turn includes the user identity 156 and a policy 159.

The interconnection of the elements of system 100 will now be described. The network 160 couples the tablet 132, the mobile 134, the mobile 152, the computer 154, the hosted service 142, the hosted service 144, and the network security system 120 in communication (indicated by solid lines). The actual communication path can be point-to-point over public and/or private networks. Some items, such as AppWrapper 157, might be delivered indirectly, e.g. via an application store (not shown). All of the communications may occur over a variety of networks, e.g. private networks, VPN, MPLS circuit, or Internet, and may use appropriate APIs and data interchange formats, e.g. REST, JSON, XML, SOAP and/or JMS. All of the communications can be encrypted. This communication is generally over a network such as the internet, inclusive of the mobile internet, via protocols such as EDGE, 3G, LTE, Wi-Fi, and WiMAX. Additionally, a variety of authorization and authentication techniques, such as username/password, OAuth, Kerberos, SecureID, digital certificates, and more, can be used to secure the communications.

Controller 121 and storage 122 can include one or more computers and computer systems coupled in communication with one another. They can also be one or more virtual computing and/or storage resources. For example, controller 121 may be one or more Amazon EC2 instances and storage 122 may be an Amazon S3 storage. Other computing-as-service platforms such as Force.com from Salesforce, Rackspace, or Heroku could be used rather than implementing network security system 120 on direct physical computers or traditional virtual machines. Additionally, to implement the functionalities 125 one or more points of presence (POPs) may be established. For example, the data plane 127 POPs may be distributed geographically and/or co-hosted with particular hosted services. Similarly, the management plane 126 POPs may be distributed geographically. The two types of POPs may be either separately hosted or co-hosted as well.

Having described the elements of FIG. 1 and their interconnections, elements of the figure will now be described in greater detail. The network security system 120 provides a variety of functionalities 125 including providing a management plane 126 and a data plane 127. Other functionalities, e.g. control plane, may also be provided. These functionalities 125 collectively provide secure network access to the hosted services 140 by client devices 150. Although we use the term network security system to describe network security system 120, more generally the system provides application visibility and control functions as well as security.

The management clients 130 according to one embodiment are computing devices with a web browser with a secure, web-delivered interface provided by the network security system 120 to define and administer policies 181. The network security system 120 according to some embodiments is a multi-tenant system, so a user of a management client can only change policies 181 associated with her organization. In some embodiments, APIs may be provided for programmatically defining and or updating policies. In such embodiments, the management clients 130 might include one or more servers, e.g. a corporate identities directory such as a Microsoft Active Directory, pushing updates and/or responding to pull requests for updates to the policies 181. Both systems may co-exist; for example, some companies may use a corporate identities directory to automate identification of users within the organization while using a web interface for tailoring policies to their needs. Management clients are assigned roles and access to the network security system 120 data is controlled based on roles, e.g. read-only vs. read-write.

The function of the network security system 120 with respect to client devices 150 is easier to describe in conjunction with FIGS. 2-3: FIG. 2 shows the virtual network topology of a system in accordance with an embodiment; FIG. 3 shows a more detailed network topology and data flow of a system in accordance with an embodiment. For both figures, an attempt by a user of computer 154 to access hosted service 142 is shown. FIG. 2 shows a conceptual view of the communication path with the network security system 120 and the data plane 127 serving to create a virtual network 260 intermediating communications between the computer 154 and the hosted service 142. FIG. 3 shows one possible network topology for the same communication with the computer 154 coupled to an ISP network 362 (optional) which is in turn coupled to a corporate network 364 (optional) which is in turn coupled to the public network 366. The public network 366 is in turn coupled to the hosted service 142, and the network security system 120 and the data plane 127. Although FIG. 3 is one possible network topology, it remains a simplified, architectural view rather than a direct network layout. For example, the networks that the hosted service 142 and the network security system 120 operate on are not shown, e.g. the service providers (also ISPs) for both are omitted. FIG. 3 includes time stamps t₁ to t₁₂ that highlight the sequential routing order that the client 155 causes requests to the hosted service 142 to take. Of particular note is that requests, such as a web browser HTTP GET request for a URL of a hosted service, are routed atypically. Specifically, the client 155 identifies the request and causes the route to go t₁ to t₄ and into the network security system 120 rather than to the hosted service 142. The network security system 120 analyzes the user identity 156 and the applicable policy before routing the request to the hosted service 142, t₅ to t₆. Notably, from the perspective of the hosted service 142, the request will go back to the network security system 120, t₇ to t₈, rather than directly to the computer 154. The network security system 120 can analyze the returned data, apply further policies in a user identity 156 dependent fashion and then return the response from the hosted service 142 to the computer 154, t₉ to t₁₂. FIG. 3 also highlights that the client 155 is compatible with—and distinct from—existing VPN, proxy and network monitoring solutions. In FIG. 3, the network access of computer 154 is being routed using a VPN solution onto the private corporate network 364. This also means that corporate proxy, firewall, and content filtering policies can generally be applied. The corporate proxy should be configured with appropriate rules to forward chain requests to the network security system 120. Additionally while FIGS. 1-3 focus on a primarily hosted network security system 120, it is possible to have an “on premise” or enterprise hosted private solution. In such an embodiment, all or portions of the network security system 120 may be completely within the corporate network.

As discussed, the corporate administrator should have previously configured the hosted service 142 to service requests for users of the corporation from the network security system 120. This prevents client devices 150 that are lacking the client 155 (or the counterparts for mobile) from bypassing the policies enforced by the network security system 120. As noted, other approaches to ensuring that hosted services are only accessed through the network security system 120 can be employed.

Returning to FIG. 1, a general view of how the network security system 120 functions has been provided. Companies, or more generally any individual or entity, wishing to better secure their use of network hosted services sign up with the network security system 120. Using a web-based interface and a computer device, the company can establish a policy in policies 181 for their users. For each user—and optionally each device—a user identity (e.g. user identity 156 stored with user identities 183) is generated by the network security system 120. The user identity 156 together with an appropriate client (e.g. client 155 selected from clients 182) are installed into the user's client device(s) 150. For example, for a computer such as computer 154, a client 155 with the user identity 156 included is loaded. For a mobile device, multiple approaches can be used: a VPN on demand 158 can be installed (included in clients 182) and/or wrapped applications such as AppWrapper 157 can be installed. These approaches will both be discussed now in greater detail.

Client Installation and Processes

The onboarding process and hosted service access provided by the network security system 120 will be described first by focusing on computer-style client devices.

Consider a user's first access with computer 154. First, an administrator must enroll the user via the management interface. In one embodiment, after enrollment by administrators, email provisioning is provided. The email includes a hyperlink or similar mechanism for the user to download and install a client that is either: (a) browser add-ons and/or (b) secure tunneling agents. Additionally, a user identity (e.g. user identity 156) and a policy (e.g. policy 159) will be provided, either embedded into the downloaded client 155 or as standalone items. The browser add-on, or extension—the terms will be used interchangeably—functions in an analogous fashion to existing web browser PAC files; however, because the specific routing is dynamic based on the policy, and client certificates representing the user identity are used, the browser add-on/extension embodiment is chosen in one embodiment. In another embodiment, the add-on regularly updates the proxy auto-config (PAC) file for the browser that contains the appropriate URLs for routing to the network security system 120 and applies the appropriate user identity information.

If a user has multiple web browsers installed, add-ons may be installed for each browser—or only for certain browsers depending on the policies set by the administrator. Here, the policy 159 is a machine-readable representation of the URLs that should be routed through the network security system 120. As discussed, supra, this is a subset of the full policy (itself a collection of dozens or hundreds of individual policies) that are defined on the network security system 120 by the user's company. Thus, the policy would indicate that URLs like Yahoo! Finance would likely not be routed to the network security system 120, while a hosted service like the corporate SaaS CRM solution, Salesforce.com would be. Because the URLs affected by the policy are kept client side, the policy 159 can also be periodically updated from the network security system 120 by the client 155. As noted, according to one embodiment the user identity 156 is a certificate that is used to sign the packets routed to the network security system 120. In other embodiments, the certificate is provided on connection with the SSL/TLS connection establishment and then packets are transmitted normally.

The secure tunneling agent client 155 is a more traditional standalone application. Whether or not it is installed is similarly configured by the administrator, e.g. in the policy for that user. The secure tunneling agent helps secure hosted services that operate outside the web browser, e.g. a Dropbox that has an application client. One embodiment divides the secure tunneling agent into two components, (i) a network driver loaded into the kernel that performs packet analysis combined with (ii) a user service that provides a secure tunnel for the packets to the network security system 120. Embodiments cache DNS results and perform reverse DNS lookups, or sniffing, to identify network requests targeted for URLs covered by the policies and to re-target those requests to the network security system 120 after signing the requests with the client certificate.

In the browser add-on case, the network security system 120 serves as an explicit proxy. In contrast, in the secure tunneling agent computer client embodiments, the network security system 120 serves a transparent proxy to the hosted service. The mobile clients similarly divide with the VPN on demand approach working like an explicit proxy while the AppWrapper approach working like a transparent proxy. The primary distinction between the process flow of FIG. 4 and that of FIG. 5 is that FIG. 4 focuses on the more client-focused (generally explicit) proxy case while FIG. 5 focuses on the more server-focused (generally transparent) proxy case.

FIG. 4 is a process flow diagram of policy enforcement focused on the client device perspective. FIG. 4 includes process 400 which begins at step 410, where the policy and user identity are received. As discussed, supra, the policy may be periodically updated. Additionally, the policy and/or user identity may be bundled into the client such as a browser add-on or a secure tunneling agent.

Process 400 continues at step 420 with a request for a URL of a hosted service being received. In the browser add-on context, the URL is directly received and subject to analysis. This may also allow for subtle differentiation, e.g. handling subdomain.domain.tld differently from www.domain.tld. In contrast, in the case of the secure tunneling agent, network packets destined to IP addresses that match the DNS resolution of a URL controlled by the policy are identified. Thus, if subdomain.domain.tld and www.domain.tld share the same network address, both will be routed even if the policy only applies to one and not the other. This type of “failure” will generally lead to over-inclusion on the client side. The over inclusion is handled appropriately on the server side.

In some embodiments, the network security system performs application signature generation to assist companies in generating policies that describe hosted services easily. Signature generation includes periodically crawling a predefined list of domains of hosted services. For each hosted service, the URLs referred to by the pages crawled that do not need an account or login are identified. This is a “whitelist” of URLs associated with a hosted service that are generally outside of the policies. Similarly, a list of domains and associated URL formats that correspond to a given hosted service can be provided, this becomes a “blacklist” of URLs. In one embodiment, the blacklist is manually maintained. Thus for a policy definition that applies to hosted service X would include URLs and/or a signature in the client-side policy of the browser add-on to make a decision about whether or not the policy applies as follows.

First, extract the domain name and URL are extracted from the HTTP request. Second if the domain name or URL is on the blacklist or contains a variation of the company identifier (e.g. if company identifier is “netskope” or “exampleco” look for “hostedservice.com/netskope” or “exampleco.hostedservice.com”) treat the request as a request for the application. Note in some embodiments, the administrator for a company can identify the company-specific identifier used for each hosted service via the management interface. Similarly, if the domain name or URL is present on the whitelist the request can be bypassed.

This approach can also be used on the server side to limit the application of policies to relevant URLs. Additionally, in some embodiments the crawling process identifies a list of URLs corresponding to login events for various hosted services. This list can assist in identifying hosted service login events.

In other embodiments, operators of hosted services may provide information to the operator of the network security system to assist in policy definition and identifying whitelists/blacklists.

Next, at step 430, the URL is selectively routed according to the policy. For URLs that are not covered by the policy, the normal host operating routing system is applied (not shown). For those that are covered by the policy, the request is signed using the user identity and routed to the network security system 120.

At step 440, the policy is applied based on the user identity 156. Counterintuitively, even prohibited hosted services and their corresponding URLs generally reach step 440 to enable server-side logging. In a similarly counterintuitive vein, deactivated user identities (including for stolen/lost devices) can be set to a “compromised” state on the network security system 120. This allows one use—or perhaps more—of the computer but denies access. Thus, a user identity that has been marked as “compromised” appears to connect to the network, specifically network security system 120, but is rebuffed by the policy at step 440 from accessing the hosted service. However, the activity and other information about the compromised client device can be logged and/or reported out. Still other embodiments may download computer programs and/or trigger programs in the client to deactivate the client device and/or to indicate to the user that that device is lost or stolen.

Returning to process 400 and step 440, a typical policy will log certain events, see infra, associated with the request and generate a new request to the hosted service (see FIG. 3 and t₅ to t₈). When the hosted service responds to that request, optionally, further policy filtering can occur.

Normally though, at step 450 the response from the hosted service is received using the client identity and sent back with the client device from the network security system 120. Note, as discussed infra, this response is typically inspected and subjected to policy before being sent back to the client device.

Notably, process 400 reinforces the points made in discussing FIGS. 2-3: conceptually (FIG. 2) there is a virtual network 260 between the computer 154 and the hosted service 142, and it is implemented (FIG. 3) with requests from the computer for the hosted service going to the network security system 120 instead of to the hosted service.

Application definitions, discussed infra, allow fine-grained control. Thus, if graphics resources for a service are hosted at a distinct URL, they can be exempted from the application definition and thus excluded from the policy.

Turning the discussion to mobile clients, as noted the primary distinction is the flexibility provided by operating system vendors to modify applications and/or install software. As noted, supra, the rationales for these restrictions are not generally technical limitations of the operating system, but rather contractual and/or embodiment decisions of the operating system vendor. For example, although the Google Chrome web browser for desktop operating systems can support an add-on client, Google Chrome for Android has add-ons turned off. Similarly, contractual rules set by Apple for the App Store limit the ability of an installed piece of software to install network drivers or modify other applications.

Thus, for mobile, two primary client embodiments are used at present. Both achieve a similar effect of providing traffic to the network security system 120 for more detailed analysis. The first embodiment is to custom-wrap the application, e.g. AppWrapper 157. Thus, instead of installing the general Dropbox client from the Apple App Store, you would install a version of the client wrapped in the mobile device management (MDM)/mobile application management (MAM) policies to tunnel traffic to the network security system 120. This approach relies on the corporate administrators' capability to wrap applications corresponding to one (or many) hosted service. Depending on the client platform, the corporate administrator may have to wrap each application individually, or alternatively leverage an application sandboxing solution to wrap multiple applications. The other embodiment is to install a VPN on demand 158. On certain platforms—most noticeably iOS—the VPN on demand 158 embodiment would tunnel all traffic, or all traffic on certain ports, to the network security system 120 when the VPN is active. On iOS, for example, this second embodiment is analogous to the approach used for network accelerators. In some other embodiment, a VPN on demand may support “split tunneling,” forwarding only select traffic to the system. In the split tunnel case, this second embodiment is functionally analogous to the secure tunneling agent client 155. Either approach ensures that the mobile client is configured to trust the SSL certificate used by the network security system 120 across multiple domains to allow something analogous to the behavior of certain proxy interception and analysis techniques.

The server-focused handling used by secure tunneling approaches is discussed in FIG. 5. FIG. 5 includes process 500 which starts at step 510 with the network security system 120 receiving an encrypted request for analysis. At step 510, the encrypted request is received and analyzed, the user identity is determined, and the packet is prepared for handling by the rest of the network security system 120. More specifically, the encrypted request is decrypted, analyzed to identify applicable policies (which are applied). Then prior to transmission to the hosted service, the communication is re-encrypted. As noted above, whereas in the computer-client case the network security system 120 was functioning more analogously to an explicit proxy, step 510 must handle the request in an analogous fashion to a transparent proxy. Additionally, user identity is typically identified in this case from the tunnel set up information this is in contrast to step 430, where at least for the explicit proxy case, the user identity information is embedded into the request that goes to the network security system itself. This dual operation of the network security system 120 is notable as are the dual mechanisms for the system to retrieve user identity information from client transmissions.

Next, at step 540 (analogous to step 440) the policy is applied. Note that, in contrast to step 440, it is more likely (if over-tunneling is occurring) that non-covered services, e.g. Yahoo! Finance, as opposed to covered services, are being routed through the network security system 120 for analysis. For services covered by the policy, appropriate event logging and policy enforcement occurs. If appropriate, the request is sent to the hosted service (or the other website), and when the response is received, the policy can optionally be applied again. Finally, at step 550 the response is sent back to the mobile client. As at step 510, precautions need to be made to handle the return response so that it is accepted by the mobile clients similarly to those made by a transparent proxy.

Points of Presence Architecture

Having discussed the functionality, the embodiment architecture used by one embodiment will be discussed in connection with FIGS. 6-7. As discussed, supra, the functionalities 125 of the network security system 120 divide into two primary groups: management plane 126 and data plane 127. Additionally, a control plane may be used. The specific division of functionality between these planes is an embodiment choice. Similarly, the functionality can be highly distributed across a number of points of presence (POPs) to improve locality, performance, and/or security. For example, either management plane or data plane POPs can be co-located with hosted services or with corporate networks.

FIG. 6 shows an architectural level schematic of a data plane point of presence. FIG. 6 includes a data plane point of presence 600 (dashed-dotted box) connected to network 610 and network 620. These can be the same networks or different networks. Network 610 is also connected to client devices 150 such as mobile 152 and computer 154. Network 620 is connected to the hosted service 142. The data plane functionality is implemented according to one embodiment with multiple computers, storage, and networking gear across multiple POPs such as data plane POP 600. The elements of data plane POP 600 include a firewall 640, a secure tunnel gateway 650 (see discussion of mobile clients, supra), a load balancer 660, multiple proxies 670, 672, and 674 (each proxy implements the policies according to the current configuration), and an outbound NAT 680. The architecture can be further scaled, e.g. multiple firewalls, etc. The proxies 670, 672 and 674 implement the specific policy, e.g. drop, reset, redirect, requests (or entire flows), as well as generate the logging messages.

The data plane POP 600 also includes a configuration agent 690 for receiving configuration and policy information from the management plane, an event queue 692 for recording and/or storing events to be sent to the management plane, and a monitoring agent 694 for monitoring the performance and status of the data plane POP 600. These items are generally coupled in communication with one or more management plane POPs, e.g. management plane POP 700 of FIG. 7, as well as the other elements of the data plane (not shown in order to focus on the data flow). Similarly, the configuration systems are not shown here. The difference between configuration and policy is that configuration information is information provided by the operator of the network security system 120, e.g. how many data plane POPs to have active, what version of the proxy software to load, etc., while policy information is provided by administrative users of the system, e.g. corporate IT personnel.

Also shown in FIG. 6 is an example of the secure tunnel 602 used by mobile 152 and other mobile clients. In contrast, the data from computer 154 is routed directly from the firewall 640 to the load balancer 660. As discussed some client types use secure tunnels (here one is being used for mobile) and others do not (here one without a secure tunnel is being used for the computer).

FIG. 7 shows an architectural level schematic of a management plane point of presence. FIG. 7 includes a management plane POP 700 to implement the management plane 126 functionality. Some embodiments may have only a single management plane POP, while others may have multiple POPs. The inter-relationship and communications with the data plane POP 600 are shown in FIG. 7 with large double-headed arrows. The communications between management clients 130 and the client devices 150 and the management plane POP 700 are similarly represented.

Management plane POP 700 includes: summary data 710, raw event data 712, configuration 714, policies 181, web management interface 730, provisioning service 740, configuration service 750, event storage service 752, monitoring service 754, and report generator 756. The services bridge the management/data planes: configuration service 750 communicates with configuration agent 690; event storage service 752 communicates with event queue 692; monitoring service 754 communicates with configuration agent 690. The report generator 756 is a management-plane-only item in this embodiment, combing the raw event data 712 to generate summary data 710 for reporting. The web management interface 730 enables administration and reporting via web browsers. The provisioning service 740 provides client devices with the appropriate client (e.g. client 155 or VPN on demand 158 from clients 182) as discussed, supra, for configuration. The provisioning service 740 may also be responsible for providing policy updates to client devices 150. In other embodiments, event storage service 752 and/or monitoring service 754 may accept data directly from hosted services and/or other sources for unified logging and reporting.

Policies and Application Definitions

Embodiments may support two primary types of individual policies: logging policies (e.g. events) and flow step policies (e.g. what happens to the user's request). The two types are related, but administrators may conceptualize them differently. Accordingly, they may be distinctly administered in some embodiments, while in other embodiments a single policy type exists with configuration options to indicate whether a given policy is one or the other type. Customers can establish defaults for what types of events are logged—note that in some embodiments event tracking occurs but is not shown to users based on their log level. Thus, a user might only want to see certain security violations, but the operator of the system may want to track all secure tunnels (e.g. secure tunnel 602) created for mobile devices. Thus, the event services would capture the event but record it in such a way that it might not be visible to the administrator.

For logging policies, the default behavior in one embodiment is for the administrator to pick a logging level from a selection of levels defined by the operator of the network security system and only events of that level (and more severe) are shown. The administrator can then tailor the logging by adding more events under certain conditions. For example, log level severe only but add policies for downloads to disk from an application or hosted service. A sample set of logging policies according to one embodiment includes the following:

Level Conditions/Options Sample Logged Event Info 1. One event Default. Applied when Network flow variables; per connection there is no more specific device info (if available); policy. system-generated flow statistics (e.g. latency/ number of bytes (etc.). 2. User/Group Based on user identifier User and group (e.g. client certificate); information; additionally, can log all activity for a unknown users can be period of time. flagged. 3. Service Based on matching Information on the specific service-specific condition application, e.g. resource, variables. (custom) condition variables, and custom triggered events. 4. Log Generally should be time- Per HTTP transaction everything limited to conserve data detailed logging. storage.

For flow action policies, there is a default to “permit” (or default to “deny”) policy and then administrators supplement the policy with application-, user-, and group-specific policies. If only one flow action policy matches, then a determination is made whether to drop, reset, or redirect a particular request (or entire flow of requests/responses). If multiple policies match, different rules can be used by the system to pick the priority, e.g. most specific policy to least specific policy (most conditions matched), first policy tested in sequence that matches (administrator can re-order), most restrictive policy outcome selected (drop wins over reset wins over redirect). Generally a policy can be considered as testing a set of match conditions and the performing one or more actions. The most common actions are permit, block (or deny), redirect (asks client to go to another site, might prompt user to request permissions from the administrator), log, reset (drops the TCP connection) and encrypt (data within application payload). Another action could be to invoke another external service integrated in the network security server or outside to process the data further. We will use “block” as a common example of a policy action in the below descriptions, but more generally any action can be applied.

Condition variables are used to determine policy matches for both logging and flow actions. The policy itself can define a match in terms of condition variables tested for a simple direct match, hierarchical parent/child matches, and/or more complex logical matches.

Turning to the condition variables, time windows can be specified (window types may also include time/date information to narrow the window):

Time Window Type Description Evaluation Always Apply policy all the Default value of policy in time. one embodiment. Weekly A day of the week. Based on calendar of the locale, e.g. Saturday. Daily A specific time within Time range in the locale, the day. e.g. 9am-5pm. User defined A window specified by Generally specified as a a start time and an full UTC date-time range, end time. e.g. a block during a three- day company shutdown could be specified for US operations.

Continuing, there are network and HTTP flow condition variables:

Variable Description Evaluation client public The public IP visible CIDR match; can also be source IP to the system. used for geolocation. client internal The internal IP used CIDR match; can also be source IP within a NAT'ed used for geolocation; network. however, administrator may want it if it is from a known network. http_req_resp_size The total size in Numerical thresholds. number of bytes. http_method The HTTP method is Match, e.g. against values sometimes useful if such as: “POST”/“GET”/ admin wants to “PUT”. disable POST.

Additionally, geolocation mapping is supported, and depending on the library/libraries used, e.g. maxmind geoip library, different condition variables may be available, e.g. city, country, region, postal code, latitude, longitude.

Application variables are linked to the application definitions which provide the signatures for specific applications. Thus, as discussed, infra, in connection with FIGS. 8-9, specific resources and even custom condition variables can be exposed on a per-application basis. Also, matches may be any of literal matches, pattern matches,

Variable Description Evaluation Application Identity of application Match; may be grouped, e.g. identifier a collection of Google-hosted (or name) services may be interlinked. Resource Identify a “resource” Match, within the scope of identifier of a hosted service; a hosted service, e.g. a (or name) resources are generally resource for hosted service defined by a URL or A does not impact flows URI path. for hosted service B. Resources correspond to method invocation for many hosted services. Custom Custom variables are Match. variables defined by application definitions to extract and store key information, e.g. a login name. Custom Custom triggers are Match. event defined by application triggers definitions to signal significant events, e.g. user login. This can trigger a “login-failed” event. Policies can be defined to take action when the custom trigger occurs. Triggers are a way to decouple policy, which may be updated more often from the application definitions. Triggers correspond to specific operations, e.g. an “edit contact” performed causes a trigger that is responded to by the policy to determine what action to take. A common, default action is to log such events. Another example of trigger is to match certain application attack signatures or confidential information like SSN or credit card.

User-related variables are another collection of condition variables:

Variable Description Evaluation User User's identifier, or name, Match. identifier from the user identity. (or name) Group A group identifier or Supports hierarchical identifier name. containment, e.g. vice (or name) president group is a subset of all employees group. Note, engine can shortcut user identifier matching in some cases, e.g. if group is denied then skip user checks. Account Sometimes a user can Match. This can also allow name have different SaaS users to have different accounts or SSO, in which permissions based on case a SaaS account can roles. For example, if a be treated as an alias. user John has a general account and a sysadmin account with hosted service X, only the sysadmin account with hosted service X might be authorized to use certain sysadmin resources.

Lastly, device and client platform condition variables are available, such as browser family (e.g., Chrome, Internet Explorer, Safari), OS family (e.g., Windows, iOS, MacOS, Linux, Android), OS subfamily (e.g. for Windows: 7 vs. Vista), device type (e.g. desktop, mobile), device subtype (e.g. for desktop: PC vs. Mac, for mobile: tablet vs. smartphone).

Application definitions of hosted services define how interactions with hosted services should be used. The language to represent application definitions is related to the Web Application Definition Language (WADL), with significant additions for purposes of providing network security systems.

The first example is shown in FIG. 8 and includes application definition 800 for Google Documents. As the short example shows, this is a relatively simple service to define with the identity (<id> XML tags) determined by simple XML matching. Next, resources are defined and an example of how a parameter URL can be parsed and parameters extracted to assign to variables is shown with <basepath> and <resource> XML tags. No triggers are used in this example since the URLs are sufficient for identifying the flow actions of concern, e.g. document access, file upload, etc. Also, in this example a custom variable for the document id is established.

Since the application definitions are defined in a simple XML markup language, they can also be provided by administrators of a corporation. For example, if the corporation has a custom hosted service, they could provide their own application definition.

FIG. 9 with application definition 900 for Dropbox provides an example of defining a more complex hosted service. Here, URLs are insufficient and triggers are added to find the request/response and make determinations. In this example, the custom variable “logine” allocates an application-specific user-persistent variable. The variable has the value type (vtype) of string. The metadata setting is informational only and indicates that it is an “email” address. Lastly the type indicates the persistence—“conn” here, meaning the variable will persist for the connection. As you can see, the login form email address is used to update the user field if later the login is successful, e.g. “<extract>” tag as well as “<find-and-update-user>” tag. In this context, “connection” refers to a high-level non-network construct (e.g. not a TCP/IP connection) but rather a series of multiple related networks requests and responses. Thus, a series of requests and responses over the course of a day could be a single connection within an application, e.g. all use of Salesforce.com within a period without logging off. One definition of a connection is to look at the application session identifier, e.g. cookie or URL parameter, used by the hosted service so that each connection corresponds to a single session identifier.

A typical user interaction with a hosted service like Salesforce.com consists of a sequence of events that occur in the context of a session. The main events of note are: (a) login—provide user credentials to hosted service to authenticate the user; (b) application transactions—execute a set of application level transactions, e.g. add leads or define new campaigns; and (c) log-out—this event terminates the session with the server. In this context an application session connects these interactions for the network security system. Deep packet inspection logic can identify these events and link policy evaluations to each transaction boundary enabling actions to be taken. Most commonly, the application session is identified by a session cookie in the HTTP header. The network security system 120 can use the session cookie to define the session.

The trigger here in this embodiment requires each valid status to be spelled out, e.g. separate match tests are required for 200 status and for 302 status. However, some embodiments may include shortcuts for matching HTTP responses, e.g. “SUCCESS”, and/or accept regular expressions for matching, e.g. “200|302”.

Having discussed the key condition variables, additional elements of policy enforcement will be considered. This section provides additional details for one embodiment of implementing step 440 of process 400 and step 540 of process 500, discussed supra.

For flow action policies, enforcement points may occur at multiple junctures. For example, a source IP range or country code geolocation enforcement can be applied when the connection is established, but a policy to block specific file uploads to an application would likely only be enforceable when HTTP POST data becomes available when the application identifier and resource identifier condition variables are set. Thus, key points for policy enforcement within the network security system include:

-   -   After connection establishment between the client and the         network security system;     -   After HTTP request URL and host received;     -   After HTTP request header, but before request data (if any)         sent;     -   After HTTP request data received;     -   After HTTP response header, but before response data sent; and     -   After HTTP request/response completion (connection may continue         in case of pipelining).

Now, we present a more detailed process view of the filtering performed at step 440 or step 540 in conjunction with FIG. 10. In terms of embodiment, FIG. 10 could be carried out by the proxies, e.g. proxy 670, 672, or 674, or the control plane portion of the data plane (not shown) directing the proxies. FIG. 10 includes process 1000, and also context 1002 is shown with dotted lines to emphasize the ongoing dynamic updates of information. The context 1002 includes connection-specific information—note process 1000 is performed separately for each connection. Thus, if a single client device has two connections to the same hosted service simultaneously, each would be handled by a separate instance of process 1000 according to one embodiment.

The list of items in context 1002 is exemplary rather than exhaustive and includes: the user (including late binding resolution based on application behaviors, see account name condition variable supra), group (similarly potentially late binding), a session identifier, an application identifier, and other condition variables. Many of these items are not available initially and are updated or refined as the connection continues.

The process 1000 starts at step 1010 with the connection commencing and the initial context 1002 being established. Next, at step 1020, a determination of whether the full user identity is available is made. Generally, the identity is available, e.g. from the client certificate. But for many hosted services and policies, additional information may be necessary. For this reason, step 1020 is revisited periodically to allow for updated actions based on late binding, e.g. information from subsequent data in the connection.

At step 1030, a determination is made whether any static policies—e.g. policies not requiring deep packet inspection or application-specific triggers (denial) match. A large percentage of policies can be enforced without needing to perform the dynamic analysis. This can reduce the processing needs. For static (denial) matches, the flow continues at step 1040 where the static policy is enforced and the data is not transmitted onward to the hosted service; if appropriate, suitable error messages/responses are transmitted back to the client device. Process flow will continue at step 1020 if additional data arrives for the same connection. Given that the policies are fine-grained and linked to application semantics, e.g. editing/downloading, it is entirely possible that denials can be followed by subsequent allowances.

Returning to step 1030, if none of the static policies matched (for denial), then the flow continues at step 1050 with dynamic analysis of the data packets of the requests/responses within the connection. Multiple packets may need to be consumed to carry out the analysis, e.g. if a policy limits downloads to 100 kilobytes (kB), multiple response packets from the hosted service may need to be received to test the policy. At step 1050, the context 1002 is also updated, see e.g. “<extract>” and “<find-and-update-user>” tags of the application definitions. When a policy (denial) matches, flow continues to step 1060 with the denial enforced, see discussion of step 1040, and flow will continue from step 1060 to step 1020. Additionally, flow will continue from step 1050 to step 1060 if all policy conditions have been tested and the flow is permitted.

The policy enforcement framework is also extensible to allow policy actions to be expanded beyond the described items. In some embodiments, for example, custom policy actions can include selective in-line scanning of data in transition to detect and prevent data leakage. In other embodiments, a policy action can invoke an anti-virus module to scan data in transit for malware and viruses. Still other embodiments, dynamically to perform operations such as selective data encryption or decryption. In one embodiment, the goal can be to ensure that sensitive data uploaded or stored in hosted services is encrypted. Thus encryption can occur on the network security system when data moves from the client to the hosted service and decryption can occur similarly occur on the network security system when data moves from the hosted service to the client. Still other embodiments, may aid with compliance with corporate policies and government regulations, e.g. HIPAA, that require local copies of data to be encrypted. Thus, a download of records, e.g. patients, customers, could be automatically encrypted by a policy triggered by the network security system before it is provided to the requesting client. The encryption (and decryption) keys or passwords can be specified in the policy and/or the third party system. For example, all draft tax returns that are downloaded could be automatically encrypted with the last four characters of a user identifier. In still other embodiments, the encryption system may have a default password for the user that is provided to the network security system. In another embodiment, the encryption is based on a key or password based on the user identity. For example, the password based on the user identity could be a corporate encryption password for a common group of users. In another embodiment, the key could be a common token, e.g. a group certificate.

In another embodiment, encryption could be performed down at the field level. For example, only encrypting social security numbers or credit card number columns in a spreadsheet. Similarly, in another embodiment, the message contents of emails might be encrypted but headers could be left alone.

Data Mining of Event Store and Anomaly Detection

The network security system generates logging information, e.g. raw event data 712, with information gleaned from the data passing through the system. FIG. 11 is an exemplary event log entry including event log entry 1100 in a JSON-style representation. Event log entry 1100 is not exhaustive of the fields that are logged, but rather highlights key fields.

Additionally, event logs from external sources can also be provided to the network security system 120. Mining of the event data can thus accomplish several key tasks:

-   -   Establish a baseline usage behavior based on criteria such as:         user, user groups, hosted service, hosted service groups, time         of day, day of week, geo-location, bandwidth usage, and latency         observed. Note the usage behaviors can be tracked per company         using the system and/or across companies.     -   Once the baseline usage behavior is established, anomalous         activities are those that do not fit the observed baseline and         could be flagged for administrators to review and take action.         Example anomalous activities include: user accesses from a         geo-locations and/or times that do not fit the baseline and         bandwidth usage by a user being very high, e.g. over two         standard deviations compared to measured baseline. Notably, the         rules are sensitive to roles, e.g. a user in a custom-defined         sales group may be afforded greater latitude to be in a         non-standard geo-location than an employee outside that group.         In some embodiments, some anomalous activities may also be         conditions to policies that companies define specific actions,         e.g. block for excessive transfer anomaly condition until an         administrator approves it.

According to one embodiment, the raw event data 712 is analyzed using machine-learning techniques to establish the baseline. Both supervised (rules based) and unsupervised (clustering) methods can be employed. The baseline data and anomalies can be presented in a human manageable format through the management interface. For example access patterns based on geo-location could be presented using a map interface with points representing users and hosted services and connective arcs showing the usage. According to another embodiment, there is an API available to mine the raw data 712. This API can be used by partners to build value added applications using the data collected by the system. Notably, the anomalies can be tracked across multiple hosted services. For example, a download of data from one service followed by an upload to a second could be an anomaly policy that is automatically detected. Other cross service policies having to do with data integrity and security can similarly be established with suitable conditions.

Conclusion and Additional Embodiments

We describe a system and various embodiments for providing security for network delivered services. As discussed, this provides for a type of virtual network between clients and hosted services with fine-grained filtering and steering linked to user identities and application-level semantics.

Some additional embodiments and features include:

-   -   Some embodiments analyze cross-service data flows, e.g. hosted         service 1 data flowing to hosted service 2.     -   Some embodiments apply behavioral analysis on a per-user basis         to identify potential intrusions and/or irregular usage.     -   Some embodiments can identify denial-of-service attacks.     -   Some embodiments provide service level agreement (SLA) reporting         back to corporations as to whether clients were able to use the         service as promised by the hosted service.     -   Some embodiments may be integrated with single sign-on (SSO)         vendors/solutions. In some instances, the SSO solution may be         used to deny access to hosted services that are not         intermediated by the network security system. In one embodiment,         the SSO vendor will invoke a “host check” process supported by         the network security system 120. The host check starts by the         SSO solution redirecting SSO-authenticated users to a “landing         page.” The landing page is a specific URL hosted, or controlled,         by the network security system 120. The landing page contains an         HTML, element (the challenge element, usually invisible) with a         (randomly) generated identifier. The identifier is typically         unique for each visit to the landing page to prevent replay         attacks. If an add-on is present on the client device, the         add-on will detect the HTML element with the identifier and         generated a response, e.g. secure hash value of the combination         of the challenge element and the add-on user ID. Embedded         javascript in the landing page can determine the validity of the         response and authorize the access only if the response is         validated.     -   Some embodiments may link user aliases within third-party         applications. This can differentiate between a user logged into         an application as jsmith@example.com and the same application as         jsmith@myisp.com. In such embodiment, a corporate administrator         may be able to tell if a particular enterprise user is using         more than one accounts to access the same hosted service. This         information can be helpful to detect “shadow IT”—use of Internet         services in the business context without the support of         corporate IT.     -   In another embodiment, the client traffic can be redirected to         the server without using a client agent or browser add-on. For         example a DNS CNAME or DNS forwarding rule for the hosted         service can resolve to the network security system. In this         embodiment, client traffic can be rerouted as follows:     -   (i) using custom hostnames under the entity's control, e.g.         hostedservice.companyname.com, that points to the network         security system,     -   (ii) customized CNAMES in the hosted service e.g.         companyname.hostedservice.com, are configured on the hosting         service to point to the network security system instead of the         hosting service itself, or     -   (iii) per hosted service DNS forwarding rules for insertion into         that company's DNS systems to use the network security system to         resolve requests for the hosted service and thus allow         redirection. In another embodiment a tunnel (e.g. generic route         encapsulation (GRE), IPSec) from the corporate perimeter         router/firewall to the network security system is provided. When         the traffic is redirected without a client side agent, the user         identification can be signaled out of band from the corporate         network to the server or the user identity can be extracted from         the service login credentials, e.g. jsmith@example.com logging         into the hosted service. In another embodiment, authentication         system logs can be reviewed to link an IP address to a username         for purposes of user identification for a given period of time.

Any data structures and code described or referenced above are stored according to many embodiments on a computer-readable storage medium, which may be any device or medium that can store code and/or data for use by a computer system. This includes, but is not limited to, volatile memory, non-volatile memory, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other media capable of storing computer-readable media now known or later developed.

The preceding description is presented to enable the making and use of the invention. Various modifications to the disclosed embodiments will be apparent, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Thus, the invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein. The scope of the invention is defined by the appended claims. 

What is claimed is:
 1. A computer-implemented method of accessing a hosted service on a client device, the method including: receiving, on a client device of an entity's user, from a network security system, a forwarding rule for modifying requests for accessing a hosted service; receiving on the client device a request for accessing the hosted service; using the forwarding rule to modify the request for accessing the hosted service and generating a modified request for accessing the hosted service; and receiving on the client device a response from the network security system.
 2. The computer-implemented method of claim 1, wherein the forwarding rule uses custom hostnames under the entity's control that are configured to reroute traffic from the client device to the network security system.
 3. The computer-implemented method of claim 2, wherein the modified request comprises the request rerouted to the network security system based on the custom hostnames.
 4. The computer-implemented method of claim 3, wherein the response comprises a response to the modified request and is sent by the network security system on behalf of the hosted service.
 5. The computer-implemented method of claim 1, wherein the forwarding rule is a canonical name record (CNAME) forwarding rule.
 6. The computer-implemented method of claim 1, wherein the forwarding rule is a domain name system (DNS) forwarding rule.
 7. A system including one or more processors coupled to memory, the memory loaded with computer instructions to access a hosted service on a client device, the instructions, when executed on the processors, implement actions comprising: receiving, on a client device of an entity's user, from a network security system, a forwarding rule for modifying requests for accessing a hosted service; receiving on the client device a request for accessing the hosted service; using the forwarding rule to modify the request for accessing the hosted service and generating a modified request for accessing the hosted service; and receiving on the client device a response from the network security system.
 8. The system of claim 7, wherein the forwarding rule uses custom hostnames under the entity's control that are configured to reroute traffic from the client device to the network security system.
 9. The system of claim 8, wherein the modified request comprises the request rerouted to the network security system based on the custom hostnames.
 10. The system of claim 9, wherein the response comprises a response to the modified request and is sent by the network security system on behalf of the hosted service.
 11. The system of claim 7, wherein the forwarding rule is a canonical name record (CNAME) forwarding rule.
 12. The system of claim 7, wherein the forwarding rule is a domain name system (DNS) forwarding rule.
 13. A non-transitory computer readable storage medium impressed with computer program instructions to access a hosted service on a client device, the instructions, when executed on a processor, implement a method comprising: receiving, on a client device of an entity's user, from a network security system, a forwarding rule for modifying requests for accessing a hosted service; receiving on the client device a request for accessing the hosted service; using the forwarding rule to modify the request for accessing the hosted service and generating a modified request for accessing the hosted service; and receiving on the client device a response from the network security system.
 14. The non-transitory computer readable storage medium of claim 13, wherein the forwarding rule uses custom hostnames under the entity's control that are configured to reroute traffic from the client device to the network security system.
 15. The non-transitory computer readable storage medium of claim 14, wherein the modified request comprises the request rerouted to the network security system based on the custom hostnames.
 16. The non-transitory computer readable storage medium of claim 15, wherein the response comprises a response to the modified request and is sent by the network security system on behalf of the hosted service.
 17. The non-transitory computer readable storage medium of claim 13, wherein the forwarding rule is a canonical name record (CNAME) forwarding rule.
 18. The non-transitory computer readable storage medium of claim 13, wherein the forwarding rule is a domain name system (DNS) forwarding rule. 